Introduction

Acceptance testing ensures that the developed software product will meet the business needs of the Product Owner/customer. These business needs are captured by the user stories in the Product Backlog that the Product Owner helped to create and prioritize. Each user story needs to be refined with more details. This is done with the creation of the Acceptance Criteria for user stories during Backlog Refinement in preparation for the next Sprint Planning session.

Learning Outcomes

• Describe the purpose of acceptance criteria and acceptance testing.
• Identify who is responsible for creating acceptance criteria and when it is done.
• Identify who is responsible for performing acceptance testing.
• Create a complete Acceptance Test Plan.

Study Resources

For your study of this topic, use these resources.

Videos

• Acceptance Criteria (2:47) by Angela Wick in Agile Product Owner Role: Techniques.

Web Articles and Blogs

• freeCodeCamp: The Acceptance Criteria for Writing Acceptance Criteria
• Given When Then (This page has a good description of each element. The references to cucumber are to the automated test framework.)
• Given When Then (This page is basic but you may be interested in other approaches like BDD and Four-Phase Testing.)
• A product owner's guide to writing acceptance criteria for user stories
• User Acceptance Testing - UAT

Wikipedia

• User acceptance testing (UAT)

Class Lecture

• Acceptance Testing

Exercises

Before-Class Exercises